Another issue:

user@server ~# mbexport mbhd.wallet.aes
MultibitHD wallet opened
Enter your passphrase: ****************************************

(node:23615) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: p.push is not a function

I'm having the same problem here:

mbexport wallet.aes.json 
MultibitHD wallet opened
Enter your passphrase: ***********

(node:1561) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
(node:1561) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Would you be interested in software that automatically finds TypeErrors caused by corner cases like this? I am building Fuzz Stati0n to do that (free for OSS) - please take a look and consider signing up for our newsletter to keep in touch

I'm also seeing this error. Anyone have a workaround yet?

multibit classic wallet opened
(node:76388) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'fromPrivate' of undefined
    at /usr/local/lib/node_modules/mbexport/build/mbexport:77:45
    at Array.forEach (<anonymous>)
    at /usr/local/lib/node_modules/mbexport/build/mbexport:72:10
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)
    at Function.Module.runMain (module.js:703:11)
    at startup (bootstrap_node.js:190:16)
    at bootstrap_node.js:662:3
(node:76388) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:76388) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

FYI - I just submitted a pull request that will solve the error @spuder mentioned (and perhaps some of the other issues as well). Of course, the maintainer would have to merge it in and publish another package, and it would seem he is MIA. Maybe I'll publish it under a different name or something.

FYI - I just submitted a pull request that will solve the error @spuder mentioned (and perhaps some of the other issues as well). Of course, the maintainer would have to merge it in and publish another package, and it would seem he is MIA. Maybe I'll publish it under a different name or something.

Do you know where I could find your version with the patches for the "fromPrivate" issue?

@bretesq - The version with my fix is at https://github.com/DavidKDeutsch/read-multibit-wallet-file

I have a multibit.key file and I´m not sure if it is an old wallet with BTC on it.
What can I do with this .key file?

@MCPCapital - I built/used this tool almost 2 years ago, so I forget the exact hoops I jumped through in order to get it to build. That being said, I still have that build on my linux box, so I pushed the generated files (plus an NPM shrinkwrap file, which is just a publishable version of package.lock) to my fork. So if you run:

 npm i -g git+https://github.com/DavidKDeutsch/read-multibit-wallet-file.git

Then it will install it directly from my fork. You should just be able to run it without building (if you already have the official one installed, you may want to uninstall it first). Note that during install you may see a bunch of errors regarding not being able to find Visual Studio and whatnot related to node-gyp, but if towards the end you see something saying "Pure JS implementation will be used," then the failures should not matter; it just means it could not create an optimized build, and when you run mbexport-rd it will simply run the js that was installed instead of an executable binary.

I tried it out on the test wallet files in the source code and it seemed to work (I don't have my old wallets around to test), so give it a shot and let me know how it works out.

Of course, it would be easier for everyone if the real package were fixed, so @bgok, if you are out there - please take a look at my pull request and publish a working version to make everyone's lives easier :)

UPDATE: I published the fix as an npm package (mbexport-rd). Still can't guarantee it will work, just that it worked a while ago on one of my wallets.

@DavidKDeutsch Thank you! You saved my hind from the multibit classic debacle.

@DavidKDeutsch Thanks for sharing your fix with the community. Unfortunately, I don't have access to the repository any more. I haven't been at KeepKey since 2018. I think that the Multibit repositories are still controlled by ShapeShift. Your repository at https://github.com/DavidKDeutsch/read-multibit-wallet-file is probably the best chance for people who need for this tool to work.